Please review and vote on the BSF 3.1 release.

The artifacts are available at:

http://people.apache.org/~sebb/bsf-3.1-RC1/

The Maven artifacts are at:

https://repository.apache.org/content/repositories/orgapache bsf-001/

The SVN tag is at:

http://svn.apache.org/repos/asf/jakarta/bsf/tags/bsf-3.1-RC1

This will be renamed following a successful vote.

Keys are here:
http://www.apache.org/dist/jakarta/bsf/KEYS

Vote will remain open for at least 72 hours.

[ ] +1 I support this release.
[ ] -1 I am against releasing the packages (must include a reason).

sebb wrote:

> Please review and vote on the BSF 3.1 release.
>
> The artifacts are available at:
>
> http://people.apache.org/~sebb/bsf-3.1-RC1/
>
> The Maven artifacts are at:
>
> https://repository.apache.org/content/repositories/orgapache bsf-001/
>
> The SVN tag is at:
>
> http://svn.apache.org/repos/asf/jakarta/bsf/tags/bsf-3.1-RC1
>
> This will be renamed following a successful vote.
>
> Keys are here:
> http://www.apache.org/dist/jakarta/bsf/KEYS
>
> Vote will remain open for at least 72 hours.
>
> [ ] +1 I support this release.
> [ ] -1 I am against releasing the packages (must include a reason).

-1, package cannot be build from source:

================= %< ==================
$ mvn clean install
<snip>
[INFO]
------------------------------------------------------------ ------------
[INFO] Building Apache BSF testing for JavaScript/E4X 1.6R7 Axiom
[INFO] task-segment: [clean, install]
[INFO]
------------------------------------------------------------ ------------
[INFO] [clean:clean {execution: default-clean}]
[INFO] [remote-resources:process {execution: default}]
Downloading:
http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/ax iom-
api/1.2.5/axiom-api-1.2.5.pom

Downloading:
http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/ax iom-
parent/1.2.5/axiom-parent-1.2.5.pom

Downloading:
http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/ax iom-
impl/1.2.5/axiom-impl-1.2.5.pom

Downloading: http://repo1.maven.org/maven2/org/wso2/wsf/javascript/axiom-
e4x/0.29/axiom-e4x-0.29.pom
[INFO] Unable to find resource 'org.wso2.wsf.javascript:axiom-e4x:pom:0.29'
in repository central (http://repo1.maven.org/maven2)
Downloading:
http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/ax iom-
api/1.2.5/axiom-api-1.2.5.jar
Downloading: http://repo1.maven.org/maven2/org/wso2/wsf/javascript/axiom-
e4x/0.29/axiom-e4x-0.29.jar

Downloading:
http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/ax iom-
impl/1.2.5/axiom-impl-1.2.5.jar
[INFO] Unable to find resource 'org.wso2.wsf.javascript:axiom-e4x:jar:0.29'
in repository central (http://repo1.maven.org/maven2)

[INFO]
------------------------------------------------------------ ------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------ ------------
[INFO] Failed to resolve dependencies for one or more projects in the
reactor. Reason: Missing:
----------
1) org.wso2.wsf.javascript:axiom-e4x:jar:0.29

Try downloading the file manually from the project website.

Then, install it using the command:
mvn install:install-file -DgroupId=org.wso2.wsf.javascript -
DartifactId=axiom-e4x -Dversion=0.29 -Dpackaging=jar -Dfile=/path/to/file

Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.wso2.wsf.javascript -
DartifactId=axiom-e4x -Dversion=0.29 -Dpackaging=jar -Dfile=/path/to/file -
Durl=[url] -DrepositoryId=[id]

Path to dependency:
1) org.apache.bsf.testing:bsf-testing-e4x-1.6R7-Axiom:jar:3.1
2) org.wso2.wsf.javascript:axiom-e4x:jar:0.29

----------
1 required artifact is missing.

for artifact:
org.apache.bsf.testing:bsf-testing-e4x-1.6R7-Axiom:jar:3.1

from the specified remote repositories:
apache.snapshots (http://repository.apache.org/snapshots),
central (http://repo1.maven.org/maven2)
================= %< ==================

BUILDING text file does not give any hint where this artifact should be
coming from.

BTW: Is BSF 3.1 now compatible with Jexl2? Jexl2 has now its own script
engine support, but BSF engines will force Jexl 1.2 in which creates
incompatibilities for Jexl2 in BSF 3.0.

- Jörg

On 18/05/2010, Jörg Schaible <joerg.schaible [at] gmx.de> wrote:
> sebb wrote:
>
> > Please review and vote on the BSF 3.1 release.
> >
> > The artifacts are available at:
> >
> > http://people.apache.org/~sebb/bsf-3.1-RC1/
> >
> > The Maven artifacts are at:
> >
> > https://repository.apache.org/content/repositories/orgapache bsf-001/
> >
> > The SVN tag is at:
> >
> > http://svn.apache.org/repos/asf/jakarta/bsf/tags/bsf-3.1-RC1
> >
> > This will be renamed following a successful vote.
> >
> > Keys are here:
> > http://www.apache.org/dist/jakarta/bsf/KEYS
> >
> > Vote will remain open for at least 72 hours.
> >
> > [ ] +1 I support this release.
> > [ ] -1 I am against releasing the packages (must include a reason).
>
>
> -1, package cannot be build from source:
>
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D %< =3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> $ mvn clean install
> <snip>
> [INFO]
> ------------------------------------------------------------ ------------
> [INFO] Building Apache BSF testing for JavaScript/E4X 1.6R7 Axiom
> [INFO] task-segment: [clean, install]
> [INFO]
> ------------------------------------------------------------ ------------
> [INFO] [clean:clean {execution: default-clean}]
> [INFO] [remote-resources:process {execution: default}]
> Downloading:
> http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/ax iom-
> api/1.2.5/axiom-api-1.2.5.pom
>
> Downloading:
> http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/ax iom-
> parent/1.2.5/axiom-parent-1.2.5.pom
>
> Downloading:
> http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/ax iom-
> impl/1.2.5/axiom-impl-1.2.5.pom
>
> Downloading: http://repo1.maven.org/maven2/org/wso2/wsf/javascript/axiom=
-
> e4x/0.29/axiom-e4x-0.29.pom
> [INFO] Unable to find resource 'org.wso2.wsf.javascript:axiom-e4x:pom:0.=
29'
> in repository central (http://repo1.maven.org/maven2)
> Downloading:
> http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/ax iom-
> api/1.2.5/axiom-api-1.2.5.jar
> Downloading: http://repo1.maven.org/maven2/org/wso2/wsf/javascript/axiom=
-
> e4x/0.29/axiom-e4x-0.29.jar
>
> Downloading:
> http://repo1.maven.org/maven2/org/apache/ws/commons/axiom/ax iom-
> impl/1.2.5/axiom-impl-1.2.5.jar
> [INFO] Unable to find resource 'org.wso2.wsf.javascript:axiom-e4x:jar:0.=
29'
> in repository central (http://repo1.maven.org/maven2)
>
> [INFO]
> ------------------------------------------------------------ ------------
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------ ------------
> [INFO] Failed to resolve dependencies for one or more projects in the
> reactor. Reason: Missing:
> ----------
> 1) org.wso2.wsf.javascript:axiom-e4x:jar:0.29
>
> Try downloading the file manually from the project website.
>
> Then, install it using the command:
> mvn install:install-file -DgroupId=3Dorg.wso2.wsf.javascript -
> DartifactId=3Daxiom-e4x -Dversion=3D0.29 -Dpackaging=3Djar -Dfile=3D/pat=
h/to/file
>
> Alternatively, if you host your own repository you can deploy the file
> there:
> mvn deploy:deploy-file -DgroupId=3Dorg.wso2.wsf.javascript -
> DartifactId=3Daxiom-e4x -Dversion=3D0.29 -Dpackaging=3Djar -Dfile=3D/pat=
h/to/file -
> Durl=3D[url] -DrepositoryId=3D[id]
>
> Path to dependency:
> 1) org.apache.bsf.testing:bsf-testing-e4x-1.6R7-Axiom:jar:3.1
> 2) org.wso2.wsf.javascript:axiom-e4x:jar:0.29
>
> ----------
> 1 required artifact is missing.
>
> for artifact:
> org.apache.bsf.testing:bsf-testing-e4x-1.6R7-Axiom:jar:3.1
>
> from the specified remote repositories:
> apache.snapshots (http://repository.apache.org/snapshots),
> central (http://repo1.maven.org/maven2)
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D %< =3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>

Rats - it builds OK for me and for Hudson - I guess those must have
got local copies.

BTW, what JVM and OS are you using?

> BUILDING text file does not give any hint where this artifact should be
> coming from.

Nor should it need to - it should be in the maven POMs.

I tidied up some of the repo dependencies as I thought I found it in centra=
l.
I assumed that Maven would tell me if the dependency could not be resolved.

Is there any way to check this, apart from deleting the local maven repo?

Try adding

<repositories>
<repository>
<id>wso2</id>
<url>http://dist.wso2.org/maven2</url>
<snapshots>
<enabled>true</enabled>
</snapshots>
</repository>
</repositories>

to testing/e4x-1.6R7-Axiom/pom.xml

and see if that allows the test to continue.

I'd like to see if there are any further problems before proceeding
with another RC.

> BTW: Is BSF 3.1 now compatible with Jexl2? Jexl2 has now its own script
> engine support, but BSF engines will force Jexl 1.2 in which creates
> incompatibilities for Jexl2 in BSF 3.0.

Start a new thread for that.

> - Jörg
>
>
> ------------------------------------------------------------ ---------
> To unsubscribe, e-mail: general-unsubscribe [at] jakarta.apache.org
> For additional commands, e-mail: general-help [at] jakarta.apache.org
>
>

Hi Sebb,

sebb wrote:


> On 18/05/2010, Jörg Schaible <joerg.schaible [at] gmx.de> wrote:

[snip]

>> 1 required artifact is missing.
>>
>> for artifact:
>> org.apache.bsf.testing:bsf-testing-e4x-1.6R7-Axiom:jar:3.1
>>
>> from the specified remote repositories:
>> apache.snapshots (http://repository.apache.org/snapshots),
>> central (http://repo1.maven.org/maven2)
>> ================= %< ==================
>>
>
> Rats - it builds OK for me and for Hudson - I guess those must have
> got local copies.
>
> BTW, what JVM and OS are you using?

Currently:
$ mvn -version
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_20
Java home: /opt/sun-jdk-1.6.0.20/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.32-gentoo-r7" arch: "i386" Family: "unix"

>> BUILDING text file does not give any hint where this artifact should be
>> coming from.
>
> Nor should it need to - it should be in the maven POMs.
>
> I tidied up some of the repo dependencies as I thought I found it in
> central. I assumed that Maven would tell me if the dependency could not be
> resolved.
>
> Is there any way to check this, apart from deleting the local maven repo?

No, but you might use an alternate settings.xml file (-s) instead that
locates the local repo somewhere else to a temporary path.

> Try adding
>
> <repositories>
> <repository>
> <id>wso2</id>
> <url>http://dist.wso2.org/maven2</url>
> <snapshots>
> <enabled>true</enabled>
> </snapshots>
> </repository>
> </repositories>
>
> to testing/e4x-1.6R7-Axiom/pom.xml
>
> and see if that allows the test to continue.

Yes, if I add this, the build runs through. However, you're aware that the
usage of repositories within the POMs is strongly discouraged and IIRC will
no longer work in M3?

> I'd like to see if there are any further problems before proceeding
> with another RC.

Fine with me, I have some more pets in my compiler zoo ... ;-)

>
>> BTW: Is BSF 3.1 now compatible with Jexl2? Jexl2 has now its own script
>> engine support, but BSF engines will force Jexl 1.2 in which creates
>> incompatibilities for Jexl2 in BSF 3.0.
>
> Start a new thread for that.

OK.

- Jörg

On 18/05/2010, Jörg Schaible <joerg.schaible [at] gmx.de> wrote:
> Hi Sebb,
>
>
> sebb wrote:
>
>
> > On 18/05/2010, Jörg Schaible <joerg.schaible [at] gmx.de> wrote:
>
>
> [snip]
>
>
> >> 1 required artifact is missing.
> >>
> >> for artifact:
> >> org.apache.bsf.testing:bsf-testing-e4x-1.6R7-Axiom:jar:3.1
> >>
> >> from the specified remote repositories:
> >> apache.snapshots (http://repository.apache.org/snapshots),
> >> central (http://repo1.maven.org/maven2)
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D %< =3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> >>
> >
> > Rats - it builds OK for me and for Hudson - I guess those must have
> > got local copies.
> >
> > BTW, what JVM and OS are you using?
>
>
> Currently:
> $ mvn -version
> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0_20
> Java home: /opt/sun-jdk-1.6.0.20/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-gentoo-r7" arch: "i386" Family: "unix"
>
>
> >> BUILDING text file does not give any hint where this artifact should=
be
> >> coming from.
> >
> > Nor should it need to - it should be in the maven POMs.
> >
> > I tidied up some of the repo dependencies as I thought I found it in
> > central. I assumed that Maven would tell me if the dependency could no=
t be
> > resolved.
> >
> > Is there any way to check this, apart from deleting the local maven re=
po?
>
>
> No, but you might use an alternate settings.xml file (-s) instead that
> locates the local repo somewhere else to a temporary path.

I might try that, thanks!

>
> > Try adding
> >
> > <repositories>
> > <repository>
> > <id>wso2</id>
> > <url>http://dist.wso2.org/maven2</url>
> > <snapshots>
> > <enabled>true</enabled>
> > </snapshots>
> > </repository>
> > </repositories>
> >
> > to testing/e4x-1.6R7-Axiom/pom.xml
> >
> > and see if that allows the test to continue.
>
>
> Yes, if I add this, the build runs through. However, you're aware that th=
e
> usage of repositories within the POMs is strongly discouraged and IIRC w=
ill
> no longer work in M3?

No, I was not aware of that.

How are such dependencies supposed to be managed then?

>
> > I'd like to see if there are any further problems before proceeding
> > with another RC.
>
>
> Fine with me, I have some more pets in my compiler zoo ... ;-)
>
>
> >
> >> BTW: Is BSF 3.1 now compatible with Jexl2? Jexl2 has now its own scr=
ipt
> >> engine support, but BSF engines will force Jexl 1.2 in which creates
> >> incompatibilities for Jexl2 in BSF 3.0.
> >
> > Start a new thread for that.
>
>
> OK.
>
>
> - Jörg
>
>
> ------------------------------------------------------------ ---------
> To unsubscribe, e-mail: general-unsubscribe [at] jakarta.apache.org
> For additional commands, e-mail: general-help [at] jakarta.apache.org
>
>

Jörg Schaible wrote:

> Hi Sebb,
>
> sebb wrote:

[snip]

>> I'd like to see if there are any further problems before proceeding
>> with another RC.
>
> Fine with me, I have some more pets in my compiler zoo ... ;-)

There's more ...

IBM 1.6.0.8:
================ %< =======================
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0
Java home: /opt/ibm-jdk-bin-1.6.0.8/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.32-gentoo-r7" arch: "x86" Family: "unix"

Running org.apache.bsf.testing.javascript.RubyTestcase
Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.258 sec
<<< FAILURE!
junit.framework.AssertionFailedError: Engine should not be null
at junit.framework.Assert.fail(Assert.java:47)
at junit.framework.Assert.assertTrue(Assert.java:20)
at junit.framework.Assert.assertNotNull(Assert.java:217)
at
org.apache.bsf.testing.javascript.RubyTestcase.testInvokeFun ction(RubyTestcase.java:41)
================ %< =======================

Sun JDK 1.7.0-ea (looks more like an incompatibility of ancient Groovy 1.1
with this JDK):
================ %< =======================
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.7.0-ea
Java home: /opt/sun-jdk-1.7.0.0_alpha69/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.32-gentoo-r7" arch: "i386" Family: "unix"

Running org.apache.bsf.testing.groovy.GroovyTestcase
Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.155 sec
<<< FAILURE!
java.lang.NoClassDefFoundError: org/mozilla/javascript/ContextFactory
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:264)
at sun.misc.Service$LazyIterator.next(Service.java:288)
at
javax.script.ScriptEngineManager.initEngines(ScriptEngineMan ager.java:127)
at javax.script.ScriptEngineManager.access$000(ScriptEngineMana ger.java:55)
at javax.script.ScriptEngineManager$1.run(ScriptEngineManager.j ava:98)
at java.security.AccessController.doPrivileged(Native Method)
at javax.script.ScriptEngineManager.init(ScriptEngineManager.ja va:96)
at javax.script.ScriptEngineManager.<init>
(ScriptEngineManager.java:69)
at
org.apache.bsf.testing.groovy.GroovyTestcase.testInvokeFunct ion(GroovyTestcase.java:34)
Caused by: java.lang.ClassNotFoundException:
org.mozilla.javascript.ContextFactory
at java.net.URLClassLoader$1.run(URLClassLoader.java:299)
at java.net.URLClassLoader$1.run(URLClassLoader.java:288)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:287)
at java.lang.ClassLoader.loadClass(ClassLoader.java:392)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:334 )
at java.lang.ClassLoader.loadClass(ClassLoader.java:332)
... 36 more
================ %< =======================

JRockit 1.5.0.14 (pathetic version, just for info):
================ %< =======================
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.5.0_14
Java home: /opt/jrockit-jdk-bin-1.5.0.14/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux" version: "2.6.32-gentoo-r7" arch: "i386" Family: "unix"
Running org.apache.bsf.testing.javascript.RubyTestcase
[JRockit] ERROR: The JVM has crashed. Writing crash information to
/home/joehni/tmp/download/bsf-3.1-src/testing/ruby/jrockit.1 2652.dump.
================ %< =======================

However, it did build fine with Sun JDK 1.6, Sun JDK 1.5 and IcedTea6 1.7.2.

Since M2.2 requires Java 5, I tried to build for JDK 1.4 (according BUILDING
file JDK 1.4 is minimum) with M2.0, but this is not possible, because the
plugins in use have a requirement for M2.1. The build with Sun JDK 1.4 and
M2.1 fails also, because another plugin uses Java 5. So *building* BSF
requires 1.5.

However, I am able to run the tests for the engines (after building with Sun
JDK 1.6) with Maven 2.1 and Blackdown 1.4.2, Sun JDK 1.4.2, JRockit 1.4. So
compatibility with JDK 1.4 looks good.

IBM JDK 1.5 and 1.4 fail as usual with Maven itself.

- Jörg

sebb wrote:

> On 18/05/2010, Jörg Schaible <joerg.schaible [at] gmx.de> wrote:

[snip]

>> Yes, if I add this, the build runs through. However, you're aware that
>> the
>> usage of repositories within the POMs is strongly discouraged and IIRC
>> will no longer work in M3?
>
> No, I was not aware of that.
>
> How are such dependencies supposed to be managed then?

The problem is that in a company environment you want normally to control
the accessed remote resources (or with a repo manager like Nexus) and with
such repository declarations arbitrary locations are added.
http://www.sonatype.com/people/2009/02/why-putting-repositor ies-in-your-
poms-is-a-bad-idea/

All you can do then is to ensure that the stuff will go to central or you
have to add the repo information to some file like BUILDING so that a user
can add the repo to its settings on its own. There have been discussions
about exceptions to the rule, but I do not know the latest status.

- Jörg

On 18/05/2010, Jörg Schaible <joerg.schaible [at] gmx.de> wrote:
> Jörg Schaible wrote:
>
> > Hi Sebb,
> >
> > sebb wrote:
>
>
> [snip]
>
>
> >> I'd like to see if there are any further problems before proceeding
> >> with another RC.
> >
> > Fine with me, I have some more pets in my compiler zoo ... ;-)
>
>
> There's more ...
>
> IBM 1.6.0.8:
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D %< =3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
> Java version: 1.6.0
>
> Java home: /opt/ibm-jdk-bin-1.6.0.8/jre
>
> Default locale: en_US, platform encoding: UTF-8
>
> OS name: "linux" version: "2.6.32-gentoo-r7" arch: "x86" Family: "unix"
>
> Running org.apache.bsf.testing.javascript.RubyTestcase
> Tests run: 1, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 2.258 se=
c
> <<< FAILURE!
> junit.framework.AssertionFailedError: Engine should not be null
> at junit.framework.Assert.fail(Assert.java:47)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at junit.framework.Assert.assertNotNull(Assert.java:217)
> at
> org.apache.bsf.testing.javascript.RubyTestcase.testInvokeFun ction(RubyTe=
stcase.java:41)

Don't know about that one.

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D %< =3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Sun JDK 1.7.0-ea (looks more like an incompatibility of ancient Groovy 1=
..1
> with this JDK):
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D %< =3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
>
> Java version: 1.7.0-ea
> Java home: /opt/sun-jdk-1.7.0.0_alpha69/jre
>
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-gentoo-r7" arch: "i386" Family: "unix"
>
>
> Running org.apache.bsf.testing.groovy.GroovyTestcase
> Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.155 se=
c
> <<< FAILURE!
> java.lang.NoClassDefFoundError: org/mozilla/javascript/ContextFactory
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at sun.misc.Service$LazyIterator.next(Service.java:288)
> at
> javax.script.ScriptEngineManager.initEngines(ScriptEngineMan ager.java:12=
7)
> at javax.script.ScriptEngineManager.access$000(ScriptEngineMana ge=
r.java:55)
> at javax.script.ScriptEngineManager$1.run(ScriptEngineManager.j av=
a:98)
> at java.security.AccessController.doPrivileged(Native Method)
> at javax.script.ScriptEngineManager.init(ScriptEngineManager.ja va=
:96)
> at javax.script.ScriptEngineManager.<init>
> (ScriptEngineManager.java:69)
> at
> org.apache.bsf.testing.groovy.GroovyTestcase.testInvokeFunct ion(GroovyTe=
stcase.java:34)
> Caused by: java.lang.ClassNotFoundException:
> org.mozilla.javascript.ContextFactory
> at java.net.URLClassLoader$1.run(URLClassLoader.java:299)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:288)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:287)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:392)
> at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:334 )
> at java.lang.ClassLoader.loadClass(ClassLoader.java:332)
> ... 36 more

That's probably because I've not allowed for Java 1.7.
Need to duplicate the fixes for Java 1.6.

However, Java 1.6+ have their own JSR-223 implementation, so there's
less need for BSF there.

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D %< =3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> JRockit 1.5.0.14 (pathetic version, just for info):
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D %< =3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
>
> Java version: 1.5.0_14
> Java home: /opt/jrockit-jdk-bin-1.5.0.14/jre
>
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "2.6.32-gentoo-r7" arch: "i386" Family: "unix"
>
> Running org.apache.bsf.testing.javascript.RubyTestcase
> [JRockit] ERROR: The JVM has crashed. Writing crash information to
> /home/joehni/tmp/download/bsf-3.1-src/testing/ruby/jrockit.1 2652.dump.

That's a JVM bug.

> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D %< =3D=3D=3D=3D=3D=3D=
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
>
> However, it did build fine with Sun JDK 1.6, Sun JDK 1.5 and IcedTea6 1.=
7.2.
>
> Since M2.2 requires Java 5, I tried to build for JDK 1.4 (according BUIL=
DING
> file JDK 1.4 is minimum) with M2.0, but this is not possible, because th=
e
> plugins in use have a requirement for M2.1.
> The build with Sun JDK 1.4 and
> M2.1 fails also, because another plugin uses Java 5. So *building* BSF
> requires 1.5.

Builds fine for me:

Apache Maven 2.1.0 (r755702; 2009-03-18 19:10:27+0000)
Java version: 1.4.2_19

I also added the java-1.4/5/6 profiles which allow cross-compilation/testin=
g.

However, I forgot to update the BUILDING file.

> However, I am able to run the tests for the engines (after building with=
Sun
> JDK 1.6) with Maven 2.1 and Blackdown 1.4.2, Sun JDK 1.4.2, JRockit 1.4.=
So
> compatibility with JDK 1.4 looks good.
>
> IBM JDK 1.5 and 1.4 fail as usual with Maven itself.
>
>
> - Jörg
>
>
> ------------------------------------------------------------ ---------
> To unsubscribe, e-mail: general-unsubscribe [at] jakarta.apache.org
> For additional commands, e-mail: general-help [at] jakarta.apache.org
>
>

On 18/05/2010, Jörg Schaible <joerg.schaible [at] gmx.de> wrote:
> sebb wrote:
>
> > On 18/05/2010, Jörg Schaible <joerg.schaible [at] gmx.de> wrote:
>
> [snip]
>
>
> >> Yes, if I add this, the build runs through. However, you're aware that
> >> the
> >> usage of repositories within the POMs is strongly discouraged and II=
RC
> >> will no longer work in M3?
> >
> > No, I was not aware of that.
> >
> > How are such dependencies supposed to be managed then?
>
>
> The problem is that in a company environment you want normally to control
> the accessed remote resources (or with a repo manager like Nexus) and wi=
th
> such repository declarations arbitrary locations are added.
> http://www.sonatype.com/people/2009/02/why-putting-repositor ies-in-your-
> poms-is-a-bad-idea/

I've read the article, and I don't think it applies here, because:
- it only affects one test project
- the test projects are not uploaded to Maven.

So I think the best is to re-instate the repo reference.

sebb wrote:

> On 18/05/2010, Jörg Schaible <joerg.schaible [at] gmx.de> wrote:
>> sebb wrote:
>>
>> > On 18/05/2010, Jörg Schaible <joerg.schaible [at] gmx.de> wrote:
>>
>> [snip]
>>
>>
>> >> Yes, if I add this, the build runs through. However, you're aware that
>> >> the
>> >> usage of repositories within the POMs is strongly discouraged and
>> >> IIRC will no longer work in M3?
>> >
>> > No, I was not aware of that.
>> >
>> > How are such dependencies supposed to be managed then?
>>
>>
>> The problem is that in a company environment you want normally to control
>> the accessed remote resources (or with a repo manager like Nexus) and
>> with such repository declarations arbitrary locations are added.
>> http://www.sonatype.com/people/2009/02/why-putting-repositor ies-in-your-
>> poms-is-a-bad-idea/
>
> I've read the article, and I don't think it applies here, because:
> - it only affects one test project
> - the test projects are not uploaded to Maven.
>
> So I think the best is to re-instate the repo reference.

It seems the discussion is still open:
http://thread.gmane.org/gmane.comp.jakarta.turbine.maven.dev el/93721

However, it is pointless for BSF 3.1 release ...

- Jörg

Hi Sebb,

sebb wrote:

> On 18/05/2010, Jörg Schaible <joerg.schaible [at] gmx.de> wrote:

[snip]

>> BTW: Is BSF 3.1 now compatible with Jexl2? Jexl2 has now its own script
>> engine support, but BSF engines will force Jexl 1.2 in which creates
>> incompatibilities for Jexl2 in BSF 3.0.
>
> Start a new thread for that.

I opened directly an issue now: BSF-32

- Jörg

Note some issues have been raised which make it prudent to do another RC.

However, it would be very helpful if someone could have a look at the
Maven artifacts to see if there are any packaging problems, so these
can be fixed before the next RC.

Equally, if there are bugs in the code, please say so now - thanks!


On 18/05/2010, sebb <sebbaz [at] gmail.com> wrote:
> Please review and vote on the BSF 3.1 release.
>
> The artifacts are available at:
>
> http://people.apache.org/~sebb/bsf-3.1-RC1/
>
> The Maven artifacts are at:
>
> https://repository.apache.org/content/repositories/orgapache bsf-001/
>
> The SVN tag is at:
>
> http://svn.apache.org/repos/asf/jakarta/bsf/tags/bsf-3.1-RC1
>
> This will be renamed following a successful vote.
>
> Keys are here:
> http://www.apache.org/dist/jakarta/bsf/KEYS
>
> Vote will remain open for at least 72 hours.
>
> [ ] +1 I support this release.
> [ ] -1 I am against releasing the packages (must include a reason).
>